Diagnostic tool with parts ordering system

ABSTRACT

A graphical user interface is provided that can be used on a diagnostic too. The graphical user interface allows a technician to operate various functions of the diagnostic tool including searching for additional information on the Internet, receiving weather information that is relevant to certain diagnostic tests, and displaying in certain formats the retrieved vehicle data and when certain vehicles were last scanned or diagnosed. The graphical user interface alerts the technician that a part solution is available for a particular retrieved diagnostic trouble code and allows the technician to order a part.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to a diagnostic tool, such as a scan tool. More particularly, the present disclosure relates to a diagnostic tool that includes parts ordering system.

BACKGROUND

In many industries, diagnostic systems play an increasingly important role in manufacturing processes, as well as in maintenance and repair throughout the lifetime of the equipment or product. Some diagnostic systems are based on personal computer technology and feature user-friendly, menu-driven diagnostic applications. These systems assist technicians and professionals at all levels in performing system diagnostics.

With equipment and products becoming more advanced, more complex, and more expensive with the addition of electronic components, the knowledge base and financial resources required to properly use, maintain, and fix these items have grown immensely. Different diagnostic systems are built with varying capabilities to perform various functions. For example, some diagnostic systems may include a simple code reader, while other diagnostic systems include complex computer architectures.

The menus on the diagnostic tools that have complex computer architectures tend to be burdensome and require a lot of navigation to return to a location so that additional functions can be performed by the diagnostic tool. Thus, there is a need for a diagnostic HUB in the form of a graphical user interface (GUI) that provides easier navigation for the user.

Accordingly, it is desirable to provide a diagnostic tool with a graphical user interface that allows a technician to diagnose the equipment or product, such as a vehicle and order replacement parts as a result of the diagnosis.

SUMMARY

The foregoing needs are met, to a great extent, by the present disclosure, wherein in one aspect of an apparatus is provided in some embodiments to include a graphical user interface with various functionality including searching capabilities; visually indicating when a vehicle was last scanned; displaying “teaser” screens; displaying which on board and off board tools or assets are available for a particular vehicle data; and changing icon display characteristics including location on the screen. The graphical user interface also allows a technician to order parts for a vehicle.

In one embodiment, a diagnostic tool with a parts ordering system is provided and can include a processor configured to execute computing instructions, a connect interface configured to connect with a connector in a vehicle and retrieve vehicle diagnostic data from the vehicle, a display in communication with the processor configured to display diagnostic information and a part solution information, a wireless communication interface in communication with the processor and configured to communicate with a remote device having a database; and a memory in communication with the processor. The memory containing instructions, that when executed by the processor causes the processor to retrieve vehicle diagnostic data including diagnostic trouble codes (DTCs), generate, on the display, a first plurality of selectable icons corresponding to individual DTCs, indicate on the display, if available, the part solution information for at least one DTC, generate, on the display, a list of top fixes based on the retrieved DTCs, search for the part solution information including availability, price and a part supplier, and generate a second selectable icon configured to allow a user to purchase the part.

In another embodiment, a non-transitory machine-readable storage medium that includes machine-readable instructions for causing a processor of a diagnostic tool to execute the method of retrieving, with the diagnostic tool, vehicle diagnostic data including diagnostic trouble codes (DTCs) from a vehicle, generating, on a display of the diagnostic tool, a first plurality of selectable icons corresponding to individual DTCs, indicating on the display, if available, a part solution information for at least one DTC, generating, on the display, a list of top fixes based on the retrieved DTCs, searching for part solution information including availability, price and a part supplier, and generating a second selectable icon configured to allow a user to purchase the part.

In still another embodiment, a computer-implemented method for ordering parts for a vehicle is provided and includes retrieving, with the diagnostic tool, vehicle diagnostic data including diagnostic trouble codes (DTCs) from the vehicle, generating, on a display of the diagnostic tool, a first plurality of selectable icons corresponding to individual DTCs, indicating on the display, if available, a part solution information for at least one DTC, generating, on the display, a list of top fixes based on the retrieved DTCs, searching for part solution information including availability, price and a part supplier and generating a second selectable icon configured to allow a user to purchase the part.

There has thus been outlined, rather broadly, certain embodiments of the disclosure in order that the detailed description thereof herein may be better understood, and in order for the present contribution to the art may be better appreciated. There are, of course, additional embodiments of the disclosure that will be described below and which will form the subject matter of the claims appended hereto.

In this respect, before explaining at least one embodiment of the disclosure in detail, it is to be understood that the disclosure is not limited in its application to the details of construction and to the arrangements of the components set forth in the following description or illustrated in the drawings. The disclosure is capable of embodiments in addition to those described and of being practiced and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein, as well as the abstract, are for the purpose of description and should not be regarded as limiting.

As such, those skilled in the art will appreciate that the conception upon which this disclosure is based may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present disclosure. It is important, therefore, that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a front view of a diagnostic tool according to an exemplary embodiment of the present disclosure.

FIG. 2 is a block diagram of the components of the diagnostic tool of FIG. 1 according to an embodiment of the disclosure.

FIG. 3 illustrates an exemplary graphical user interface (GUI) according to an embodiment of the disclosure.

FIG. 4 illustrates another exemplary GUI according to an embodiment of the disclosure.

FIG. 5 illustrates a screen illustrating various panels according to an embodiment of the disclosure.

FIG. 6 illustrates a screen having on board and off-board indicators according to an embodiment of the disclosure.

FIG. 7 illustrates a GUI having icons with vehicle diagnostic data according to an embodiment of the disclosure

FIG. 8 illustrates a GUI having various data stream icons according to an embodiment of the disclosure.

FIG. 9 illustrates a GUI having its icons rearranged according to an embodiment of the disclosure.

FIG. 10 illustrates a full screen of the data icon of FIG. 8 according to embodiment of the disclosure.

FIG. 11 illustrates a GUI displaying diagnostic trouble codes according to embodiment of the disclosure.

FIG. 12 illustrates a user selecting an icon according to embodiment of the disclosure.

FIG. 13 illustrates a user selecting an icon according to embodiment of the disclosure.

FIG. 14 illustrates a user selecting an icon according to embodiment of the disclosure.

FIG. 15 illustrates a user ordering a part according to embodiment of the disclosure.

DETAILED DESCRIPTION

The disclosure will now be described with reference to the drawing figures, in which like reference numerals refer to like parts throughout. An embodiment in accordance with the present disclosure provides a graphical interface for use on a computing device, such as a diagnostic tool, notebook, tablet, smart phone and the like.

FIG. 1 illustrates a front view of a diagnostic tool 100 according to an embodiment of the disclosure. An example of the diagnostic tool is the Genisys® Touch from Service Solutions U.S. LLC (Owatonna, Minn.). The diagnostic tool 100 may include a housing 102, a display 104, a function button or a user interface 106, a power button 108, gripping portions 110 having a finger (thumb) receiving portion 112, a camera 114 and graphical user interface 300 (discussed below). The power button 108 can also be used to put the diagnostic tool 100 into a standby mode in order to save battery power when not in use.

The gripping portions 110 may be made of a polymer including hydrogels for easy gripping. The finger-receiving portion 112 may be configured to receive a finger, such as a thumb of the user, to assist in better gripping of the diagnostic tool 100. The function button or user interface 106 may be configured for any function desired by the user including enter, back, forward, left, right, up, down, transmit, receive, return, start over, and the like. The function button can also include multiple functions of any combination of functions, such as enter and then back, etc. The user interface 106 may also include a keyboard having numbers and letters and/or be alphanumeric and the like.

The display 104 can be any type of display including a touch screen display, LCD, LED, VGA, OLED, SVGA, and other types of displays. The display 104 may be a colored, non-colored (e.g. gray scale), or a combination of both. The display 104 can display information such as the make, model, year of vehicle that the diagnostic tool 100 can diagnose, the various diagnostic tests the diagnostic tool can run, diagnostic data the diagnostic tool has received, the baseline data of the various components in a vehicle, part images, parts information, and information from remote servers (internet, database information, etc.). Additionally, the display can show videos for the user to view, and the accompanying audio can be heard via the built in speakers (not shown). The speakers can be a single speaker or multiple speakers for stereo sound. A microphone (not shown) may be included and allows the technician to record information such as the noise being made by the vehicle for later analysis or for comparison with stored data. Further, the technician can also record comments or notes during the testing for later retrieval and analysis.

In one embodiment, the display allows the user to input selection through the touch screen for interactive navigation and selection, wherein the technician can select a menu item or icons (further discussed below) by touching the selection on the graphical user interface (GUI) 300. Additionally, the display 104, when tapped or touched, can also be used to wake up the diagnostic tool 100 if it is in a sleep mode.

The camera 114 may be positioned to face the user so that the user may conduct a video chat with another person at a remote location. The camera may also be positioned on any surface of the diagnostic tool 100 including on the opposite side of display 104 so that images of parts of an engine or any components desired by the user can be taken.

FIG. 2 is a block diagram of the components of the diagnostic tool 100 of FIG. 1 according to an embodiment of the disclosure. In FIG. 2, the diagnostic tool 100 according to an embodiment of the disclosure may include a camera 114, a processor 202, a field programmable gate array (FPGA) 214, a first system bus 224, the display 104, a complex programmable logic device (CPLD) 206, the input device 106 or function button, a memory 208, an internal non-volatile memory (NVM) 218 having a database 212 with software program, a card reader 220, a second system bus 222, a connector interface 211, a selectable signal translator 210, a GPS antenna 232, a GPS receiver 234, an optional altimeter 236, and a wireless communication circuit 238.

The wireless communication circuit 238 can be configured to communicate wirelessly with a vehicle communication interface that is coupled to the vehicle's data link connector (both not shown) or another remote device. The vehicle communication interface sends signals and vehicle data received from the various electronic control units (ECUs) in the vehicle. Wireless communication circuit 238 communicates with the processor 202 via the second system bus 222. The wireless communication circuit 238 can be configured to communicate via RF (radio frequency), satellites, cellular phones (analog or digital), Bluetooth®, Wi-Fi, Infrared, ZigBee, Local Area Networks (LAN), WLAN (Wireless Local Area Network), NFC (near field communication), other wireless communication configurations and standards, or a combination thereof. The wireless communication circuit 238 allows the diagnostic tool 100 to communicate with other devices wirelessly such as with a remote computing device (not shown) having remote databases. The wireless communication circuit 238 includes an antenna or transceiver built therein (not shown) and being housed within the housing 102 or can be externally located on the housing 102.

Signal translator 210 conditions signals received from an ECU unit through the wireless communication circuit 238 to a conditioned signal compatible with diagnostic tool 100. Signal translator 210 can communicate with, for example, the following communication protocols: J1850 (VPM and PWM), ISO 9141-2 signal, communication collision detection (CCD) (e.g., Chrysler collision detection), data communication links (DCL), serial communication interface (SCI), Controller Area Network (CAN), Keyword 2000 (ISO 14230-4), OBD II or other communication protocols that are implemented in a vehicle.

The circuitry to translate and send in a particular communication protocol can be selected by FPGA 214 (e.g., by tri-stating unused transceivers). Signal translator 210 may be also coupled to FPGA 214 and the card reader 220 via the first system bus 224. FPGA 214 transmits to and receives signals (i.e., messages) from the ECU unit through signal translator 210 and the wireless communication circuit 238.

The FPGA 214 may be coupled to the processor 202 through various address, data and control lines by the second system bus 222. FPGA 214 is also coupled to the card reader 220 through the first system bus 224. The processor 202 may also be coupled to the display 104 in order to output the desired information to the user. The processor 202 communicates with the CPLD 206 through the second system bus 222. Additionally, the processor 202 may be programmed to receive input from the user through the input device 106 via the CPLD 206 or via the touchscreen display 104. The CPLD 206 may provide logic for decoding various inputs from the user of the diagnostic tool 100 and also provides glue-logic for various other interfacing tasks.

Memory 208 and internal non-volatile memory 218 may be coupled to the second system bus 222, which allows for communication with the processor 202 and FPGA 214. Memory 208 can include an application dependent amount of dynamic random access memory (DRAM), a hard drive, and/or read only memory (ROM). Software to run the diagnostic tool 100 including the GUI can be stored in the memory 208 or 218, including any other database. The database 212 can include diagnostic information and other information related to vehicles.

Internal non-volatile memory 218 can be an electrically erasable programmable read-only memory (EEPROM), flash ROM, or other similar memory. Internal non-volatile memory 218 can provide, for example, storage for boot code, self-diagnostics, various drivers, and space for FPGA images, if desired. Additionally, the internal non-volatile memory 218 may also include software such as a graphics module for rendering and displaying graphics (e.g. icons or modules) on the touchscreen display 104. If less than all of the modules are implemented in FPGA 214, memory 218 can contain downloadable images so that FPGA 214 can be reconfigured for a different group of communication protocols.

A GPS antenna 232 and GPS receiver 234 can be included and may be mounted in or on the housing 102 or any combination thereof. The GPS antenna 232 electronically couples to the GPS receiver 234 and allows the GPS receiver to communicate (detects and decodes signals) with various satellites that orbit the Earth. In one embodiment, the GPS antenna 232 and GPS receiver 234 are one device instead of two. The GPS receiver 234 and GPS antenna 232 may electronically couple to the processor 202, which may be coupled to memory 208, 218 or a memory card in the card reader 220. The memories can be used to store cartographic data, such as electronic maps. The diagnostic tool can include all the maps for the U.S. (or country of use), North America, or can have the region or state where the diagnostic tool is located. In alternative embodiments, the diagnostic tool can have all the maps of the world or any portion of the world desired by the user. This allows the diagnostic tool to be a GPS device so that a driver can drive from one location to another. The maps may be overlay or may incorporate traffic, local events, and location of other GPS devices (smart phones), and other information that can be useful to the technician. By being able to locate other diagnostic tools with GPS, then the technicians may be able to use the diagnostic tools to locate each other in order to conduct a meeting or have a social event.

The GPS receiver communicates with and “locks on” to a certain number of satellites in order to have a “fix” on its global location. Once the location is fixed, the GPS receiver, with the help of the processor, can determine the exact location including longitude, latitude, altitude, velocity of movement, and other navigational data of the diagnostic tool 100.

Should the GPS receiver be unable to lock onto the minimum number of satellites to determine the altitude or unable to determine the altitude for any reason, the altimeter 236 can be used to determine the altitude of the diagnostic tool 100. The altimeter 236 is electronically coupled to the processor 202 and can provide the altitude or elevation of the diagnostic tool 100. The altimeter 236 can be coupled to a barometric pressure sensor (not shown) in order to calibrate the elevation measurements determined by the altimeter. The sensor can be positioned interior or exterior to the housing 102 of the diagnostic tool 100. Minor atmospheric pressure changes can affect the accuracy of the altimeter 236, thus, diagnostic tool can correct for these changes by using the sensor in conjunction with the altimeter 236 along with a correction factor known in the art.

In an alternative embodiment, a vehicle communication interface 230 of the vehicle under test is in communication with the diagnostic tool 100 through connector interface 211 via an external cable (not shown). Selectable signal translator communicates with the vehicle communication interface 230 through the connector interface 211.

FIG. 3 illustrates an exemplary graphical user interface (GUI) 300 according to an embodiment of the disclosure. The GUI 300 may include various icons, information banner, modules, interface elements, and the like. The icons or modules may be activated by touching with a finger or a stylus and the like on the display 104 or through the user interface 106. The display 104 can be touch sensitive and is able to interpret finger contacts, finger tap gestures, finger swipe gestures, stylus movements, any combination thereof, and the like. It should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture may be replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). A further embodiment, a tap gesture may be replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice may be used simultaneously, or a mouse and finger contacts may be used simultaneously.

GUI 300 includes information banner 302 and icons or modules 306, 310, 312, 314, 316, 318, 320, and 322 (discussed below). In this example, information banner 302 provides information regarding the current vehicle under test, such as a 2009 Volkswagen Passat or any other vehicle. The information banner 302 includes new vehicle icon 320, which when selected enables a technician or user to enter information regarding the new vehicle. The entered information may include VIN (vehicle identification number), or other identifying information. OBDII icon 322 may be used to initiate a scan of the vehicle under test. In alternative embodiment, the scan is conducted automatically when the diagnostic tool 100 is coupled to a data link connector in a vehicle. The data link connector (not shown) provides access to various ECUs (electronic control unit) in the vehicle.

A text field 304 may also be present on the GUI 300. In one embodiment, the text field 304 may be a search field, in which the technician can enter keywords or terms to search using a search engine such as Google™ Bing™, Yahoo™ and the like. The search term or keywords may be entered into the text field 304 using the keypad 106 or a virtual keypad 106 that may appear when the text field 304 is touched with a finger or stylus. By having the text field 304, the technician can search for fixes, terms, bulletins, parts include location and pricing of the parts, or any other information in order to complete the diagnosis. The text field 304 may also be used to search any other information or topic such as baseball scores, news, weather, and the like. Once the search term or keyword is entered, the technician may touch the search icon 305 to start the search. In another embodiment, before or after the technician types in the text field 304, he can change the default search engine by tapping or touching search icon 305, which can cycle through or display the various search engines for selection.

Other icons or modules that may be display on the GUI 300 may include the diagnostic icon 306, maintenance test icon 310, scope icon 312, road test icon 314, symptom assist icon 316, and services and setting icon 318. There may be as many icons as the user desires. The diagnostic icon 306 when pressed or touched may bring up various diagnostic tests, such as sensor tests, emissions tests, or throttle position tests and the like. The maintenance test icon 310 when touched may perform maintenance tests such as inspection and maintenance and may retrieve I/M related emissions DTCs or monitors. Scope icon 312 when pressed may gather data from the scope such as an oscilloscope (automotive scope 3840F from Service Solutions U.S. LLC) attached to a portion of the vehicle under test.

Road test icon 314, when tapped, may put the diagnostic tool 100 into road test mode in order to gather vehicle diagnostic data during a road test. The road test allows a technician to gather vehicle data that may occur only during a road test such as intermittent stuttering of the vehicle at 30 mph. Symptom assist icon 316 allows the technician to access on board or off-board diagnostic databases (discussed below) in order to assist the technician to diagnose an issue with the vehicle. Services and settings icon 318 allows the technician to change the settings in the diagnostic tool. The settings may include certain preferences such as units of measurements in metrics or U.S. units (discussed below).

Each of the icons discussed herein may have an indicator 308 that indicates that additional information is available related to the functionality of that particular icon or that a certain number of updates are available. For example, the indicator 308 for the symptom assist icon 316 shows 108 different available information that available at various databases to help to identify symptoms found in the vehicle. The available information may include top fixes, bulletins, videos, number of responses from a chat room or messages that have not been viewed, and the like that may be related to the vehicle data retrieved in order to help the technician to diagnose the symptoms.

A message banner 330 may also be present on the GUI 300. The message banner 330 may include information such as the date and the weather conditions at the location of the diagnostic tool 100. The message banner 330 may contain or display information desired by the user, including alerts, news feeds, and weather at a different location or any other customizable information. The location may be based on the GPS location of the vehicle or diagnostic tool 100. It may also be based on location of the Wi-Fi connection or cellular connection to which the diagnostic tool 100 is connected to.

By knowing the weather condition, the diagnostic tool 100 can assist the technician in performing certain tests or alert the technician that the weather conditions are not optimal or may interfere with certain tests. For example, the weather may be too cold or too hot to run a vehicle battery test. The temperature may be measured optionally by a temperature sensor located on a surface of the diagnostic tool 100 or maybe received from an Internet-based source, such as www.weather.com and the like. Additional weather-related information may include barometric pressure and humidity levels, all of which may affect the testing be conducted by the technician.

FIG. 4 illustrates another exemplary GUI 400 according to an embodiment of the disclosure. Icons or modules 402, 404, 406, 408, 410, 412, 414, 416, 418, 420, 422, 424, 426, and 428 are shown on GUI 400. New vehicle icon 402 when pressed allows the technician enter new vehicle. Alternatively, pressing of the new vehicle icon 402 may allow vehicle information to be transferred from another diagnostic tool to this diagnostic tool 100. AutoID icon 404 when pressed will instruct the diagnostic tool to perform the AutoID function and retrieve certain information such as VIN number from an ECU in a vehicle. Additional disclosure regarding AutoID can be found in an application entitled “SYSTEM AND METHOD FOR AUTOMATED VEHICLE SELECTION AND AUTOMATED FIX DETECTION,” having U.S. patent application Ser. No. 13/606,850, filed on Sep. 7, 2012, the disclosure is hereby incorporated by reference in its entirety.

Heavy-duty icon 406 when pressed may bring up different icons in order to diagnose heavy-duty vehicles such as an 18-wheeler. VIN icon 408 when pressed may bring up a virtual keyboard 106 in order for a technician to enter vehicle identification number (VIN) and search for the corresponding vehicle that matches the VIN. Cancel icon 410 when pressed will cancel a function that was previously requested by user.

Vehicle icons or modules 412, 414, 416, 418, 420, 422, 424, 426, and 428 are icons or modules related to vehicles that are under test or previously tested. These icons may be arranged in the order of when the vehicle was last scanned or diagnosed. For example, vehicle icon 412 located in the top left-hand corner may be an icon of the vehicle currently being scanned or diagnosed by the technician. This may be indicated by a text on the icon such as “currently selected,” or similar text. Vehicle icon 414 also shows a vehicle (Cadillac) that was scanned or diagnosed “2 hours ago.”

Additionally, in one embodiment, vehicle icon 416 shows a vehicle (Mini) that was scanned or diagnosed “4 hours ago.” It should be noted that these icons 412, 414 and 416 are shown “brightly lit,” and icon 412 is the “brightest” compared to vehicle icons 418, 420, 422, and 424 which show that the respective vehicles were last scanned or diagnosed “yesterday,” and thus, appear to decrease in brightness or starting to fade out. As more time since the last scan or diagnosis for respective vehicles passes, the vehicle icons fade even further. For example, vehicle icons 426 and 428 show the date on which the respective vehicles were last scanned or diagnosed and thus is further decreased in brightness or more faded out than the vehicle icons 418, 420, 422, and 424. The amount time that passes in which a vehicle was last scanned or diagnosed will determine the amount of decrease in brightness, or alternatively increase in brightness, for the respective vehicle icon. The amount time may be set as desired by the technician and may be in terms of minutes, hours, days, weeks, years, decades, and the like. Additionally, although in one embodiment, the far left vehicle icon may be the brightest, the placement of the brightest vehicle icon may be to the right. This allows technicians in other countries (such as Japan) or culture or personal preferences that may read from right to left to place the brightest icon in the far right-hand corner of the GUI 400. This may be done by using the services and settings icon 318 (FIG. 3).

FIG. 5 illustrates a screen 500 illustrating various panels 502, 504, 506 according to an embodiment of the disclosure. In this embodiment, screen 500 illustrates a main panel 502 along with certain icons or modules that relate to a certain function or parameter such as system information. Right side panel 504 is shown as a “teaser” screen, which gives the technician a sneak peak of what icons or modules may be contained on the right side panel 504, such as parts information. For example, the icons or information may relate to parts such as schematics, videos, pictures, or the ability to purchase the parts based on a diagnosis that may be of interest to the technician. In the event the technician would like to see the icons or information contained on right side panel 504, he can simply swipe to the left using his finger or fingers and the right side panel 504 will replace the main panel 502 as the main panel. Any amount of the right side panel 504 may appear on screen 500 as desired by the user. Additionally, an identifier can be visible on the right side panel that is shown on screen 500 so that the user knows or can guess what icons or information may be contained on the right side panel 504.

In another embodiment, a left side panel 506 may also be present in conjunction with the right side panel 504. Alternatively, only the left side panel 506 or the right side panel 504 in conjunction with main panel 502 are displayed on screen 500. Similar to the functionality of the right side panel 504, the left side panel 506 may also be a “teaser” screen that allows the technician to know or guess what icons or information may be contained on the left side panel 506. An identifier can be located on the right side or the upper right side of the left side panel 506 so that the technician knows what icons are on the left side panel 506.

Alternatively, the left and right side panels 504, 506 may also be positioned above or below main panel 502. By having these “teaser” screens or panels, they may replace the vertical menus selection that are typically used in menus and make them horizontal for faster viewing. Thus, left and right side panels 504, 506 may also be a continuation of additional icons under the same information category such as additional icons for diagnosing a vehicle that could not be displayed on one panel.

FIG. 6 illustrates a screen 600 having on board and off-board indicators according to an embodiment of the disclosure. Message banner 606 may show information about the vehicle that is currently under test. In the screen 600, the diagnostic tool 100 has retrieved a DTC, such as P0010 as shown on message banner 602. A description box 604 may “pop out” when an icon 608 such as the description icon is pressed by the technician. Description box 604 can provide additional information about the P0100 DTC that is set in the vehicle. Additionally, icons 608 on the left side of the screen 600 indicate to the user that certain on board tools or databases are available that relates to that particular DTC or issue that the technician is trying to diagnose. One such database can be the “code assist” that may exist in database 212 (FIG. 2). On the right side of the screen 600, icons 610 indicate to the user that certain off-board databases such as iATN™, Google™, Direct-Hit™ and Symptom-Assist™ are available that relates to that particular DTC or issue. By displaying on screen 600 both on board tools in the form of icons 608 and off-board tools in the form of icons 610, the technician can select the proper database or by preference. The proper database may be based on the time in which it takes to retrieve the additional information to diagnose the component that caused the DTC to be set in the ECU. For example, it may be faster to retrieve the additional information from an onboard tool versus and off-board tool, which may require the technician to have a wired or wireless connection to request the information from a remote server or computing device on which the off-board database is stored. Thus in this embodiment, if one or both of the tools are available, the technician can decide which tool to use is best for him. Additionally, the technician may prefer to use the off-board tools as they may be updated more often than the onboard tools.

FIG. 7 illustrates a GUI 700 having icons with vehicle diagnostic data according to an embodiment of the disclosure. GUI 700 includes a message banner 702 showing data stream engine. Icons or modules 704, 706, 708, 712 and 716 can be vehicle data icons showing various retrieved vehicle data. For example, icon 704 shows vehicle diagnostic data regarding vehicle speed, icon 706 shows intake air temperature, icon 708 shows fuel tank pressure, icon 712 shows manifold absolute pressure, and icon 716 shows throttle position.

The vehicle diagnostic data icons may show the data in various forms including numerical 714, percentage 720, graph 710, and the like. The forms may be changed by the technician by tapping on the respective icon or a portion of the icon containing the numerical 714, percentage 720, or graph 710 in order to change from one form to another. Additionally, the forms and icons may also be changed as to color, size, shading, and the like depending on the preferences of the technician. The numerical unit 714 shown on the forms for example may be changed from metrics to U.S. units and vice versa by also tapping the respective icon or portion of the icon. Further, the title of the respective icons may change in color to indicate whether the data value is within, over or under a predetermined range for the particular data value being recorded. The color may be blue for within the predetermined range, red for being over the predetermined range, and yellow for under the predetermined range. However, any color can be used to signify the data value in relation to the predetermined range as desired by the technician.

In another embodiment, all the icons or individual icon can be programmed or customized to show only metrics or U.S. units or both. The icons can also be programmed to show metrics based on the manufacturer of the vehicle under test, such as BMW, or U.S. units for US manufacture such as Ford. Further the icons can also be programmed to show metrics or U.S. units depending on the location of the diagnostic tool 100, based on user preference as part of a login ID or the language selected for the diagnostic tool.

Also shown on FIG. 7, is a hand 718 representing a hand or a finger of the technician moving icon 716. The GUI 700 may change depending on the preference of the user. That is, the respective icons or modules 704, 706, 708, 712, and 716 may be moved to other portions of the GUI 700. Movement of the icon may be done with finger, stylus, user interface 106, or the like. The GUI 700 is configured to move the other respective icons in relation to the icon (in this case 716) in order to place the icon at a location on GUI 700 as desired by the technician.

Further, the icon may be placed at an angle as shown in FIG. 7. Because icon 716 appears at an angle different from the remaining icons this may quickly attract the eyes of the technician in order to quickly view the icon that he's really interested in. This may be helpful when the data changes rapidly and the technician wants to be sure to focus on that icon.

FIG. 8 illustrates GUI 800 having various data stream icons according to an embodiment of the disclosure. GUI 800 includes a message banner 802 showing a data stream that is being recorded by the diagnostic tool 100. The data icons shown in GUI 800 include data icon 804 for A/C clutch, data icon 806 for throttle position, data icon 808 for fuel tank pressure, data icon 810 for manifold absolute pressure, and data icon 812 for idle air control position. As previously discussed, these icons may include numerical, graphical, percentage and the like to show the data being retrieved.

In one embodiment, in the event that the user would like to zoom in to see a larger display of information about the data on a particular icon, he may simply use one or 2 finger gestures to make the portion of the GUI or icon bigger. Alternatively, the user can also make a particular icon smaller by using one or 2 finger gestures.

FIG. 9 illustrates GUI 800 having its icon rearranged according to an embodiment of the disclosure. As shown in FIG. 9, GUI 800 has now been changed based on a gesture via finger(s) and/or stylus, and the like so that data icon 808 is now larger or is zoomed in in relation to the other icons on GUI 800. The remaining data icons 804, 806, 810, 812 have been rearranged or repositioned to accommodate the now larger data icon 808. The remaining data icons 804, 806, 810, 812 may be repositioned to fill the remaining portion of the GUI 800 as shown in FIG. 9 or can be repositioned to fill only a portion of the GUI 800.

FIG. 10 illustrates a full screen of the data icon 808 of FIG. 8 according to embodiment of the disclosure. In the event that the user would like to view the data icon, such as data icon 808 in a full view mode, the user may use a gesture via finger(s) and/or stylus and the like to make the data icon 808 as large or small as he likes. In full view mode, the entire GUI 800 shows only the icon 808 and its data or only the data/graph part.

FIG. 11 illustrates a GUI 1100 displaying diagnostic trouble codes (DTC) according to embodiment of the disclosure. The DTCs are pulled from a vehicle electronic control unit using the diagnostic tool 100. The DTCs may be generic, manufacture, or vehicle specific depending on the code.

The GUI 1100 includes the message banner 1102 that may show information about the vehicle that is currently under test. A message banner 1120 describing the GUI 1100 may display a message “diagnostic trouble codes” on the GUI 1100. Each diagnostic trouble code (DTC) 1104, 1106, 1108, 1110, 1112, 1114, 1116, and 1118 are presented as individual icons. Each individual icon (1104-1118) may include information such as the diagnostic trouble code number and a description of the code and an indicator 1122 (similar to 308, as discussed above) that indicates the number of additional information (if any) that is available for each of the DTC icon. When the DTC is pulled from the vehicle, the diagnostic tool 100 can automatically (or manually selected) search a database (on the tool or remote from the hotel) to determine if additional information is available including part information or solution.

Each individual icon (1104-1118) may include information on whether a part solution is available for that particular DTC. The part solution may be relevant to only one DTC or multiple DTCs. The part solution database 212 may be stored in the memory 218 of the diagnostic tool or on a remote computing device, such as a server. For example, icon 1104 can be highlighted, for example via bold lettering, flashing, colored (partially or entirely) background of the text for the icon, any combination thereof, and the like. In other embodiments, the icon 1104 may include other appearance dressings, such as glowing, shadowing or appearing in 3-D or any other appearance dressing that makes icon 1104 noticeable to the user. This allows a user, such as a technician to be alerted that a part solution is available. The color may be any color including green, blue, red and others. Additionally each of the colors may also correspond to the history information for each code as discussed below.

Additionally, each individual icon can also include history information 1124 about when the DTC was set, such as “failed since last clear,” “current code,” and “history code,” and others. This allows the technician to know if the DTC is an old code (“history code”), a new or (“current code,”) or that the code was previously cleared from the vehicle but has since failed again (“failed since last clear”). Knowing the history of the code will assist the technician to better diagnose the vehicle.

FIG. 12 illustrates a user selecting an icon according to embodiment of the disclosure. Once the user is aware the part solution is available through color indicator, the user can select the appropriate icon. Selection may be done via a hand 1126 gesture, the stylus or via the user interface 106. Once the selection has occurred, GUI 1300 may appear on the display of the diagnostic tool.

FIG. 13 illustrates a user selecting an icon 1302 according to embodiment of the disclosure. GUI 1300 is similar to screen 600 (FIG. 6) described above but now includes the “Code-Assist Part ID™” icon 1302. Again selection may be done via a hand 1126 gesture, the stylus or via the user interface 106. Additionally, GUI 1300 includes description of the DTC. The information for the “Code-Assist Part ID™” may be on board the diagnostic tool or off-board. This “Code-Assist Part ID™” database may include DTCs information linked with various parts that could cause the DTCs to be set in the vehicle. Once the selection has occurred, GUI 1400 may appear on the display of the diagnostic tool.

FIG. 14 illustrates a user selecting an icon 1306 according to embodiment of the disclosure. GUI 1400 includes information panel 1304 from the “Code-Assist™” database (on or remote of the tool) that displays the top fixes for that particular DTC. In this case, the top reported fix includes replacing variable camshaft timing (VTC) solenoid. Additional fixes icons 1306 such as frequently reported fixes, for example, include replace engine oil, replace camshaft sensor, flush engine oiling system, replace engine oil filter, and clean throttle body. The reported fixes may be ranked in any order including from the most reported fix to the least, the most expensive fix to the least expensive fix, the least expensive fix to the most expensive fix, and the like. In one embodiment, the ranking may be displayed from left to right, right to left, top to bottom, bottom to top, and the like. GUI 1400 assists the technician in selecting the proper fix for the technician. Similarly, selection may be done via a hand 1126 gesture, the stylus, or via the user interface 106. Once the user selects a particular fix, GUI 1500 may appear.

FIG. 15 illustrates a user ordering a part according to embodiment of the disclosure. GUI 1500 may appear after the selection described in FIG. 14 is made. GUI 1500 may include a body 1502 that includes additional information about the part being ordered. Information can include how many results returned from the searching for the part. The search can be of any database (including on board database that may have been recently downloaded), such as the ones described herein using any of the search engines described herein.

In this case, the body 1502 illustrates two results were returned. However, additional results may be returned based on selection criteria (discussed herein) of the technician or the default selections on the diagnostic tool 100. Additional information that may be found in body 1502 may include availability of the part, a description of the product including part number, manual for the part, warranty information for the part, picture of the part, video of the functions of the part and how to remove and install the part, the materials that the part is made of, and manufacturer, manufacturing location of the part and other part information.

In another embodiment, the additional information about the part can include rating of the part such as quality level, top selling level, most part searched, best overall price, best substitute part to the original part and the like. Further, past and current purchasers may also provide comments about the part, such as compatibility, ease of installation, additional tools that may be needed to install the part, complaints and the like. The user may also select the desired quantity of the part and delivery method, such as same-day delivery, next day delivery, second day delivery, third day delivery, by mail, express shipping and the like. Additionally, the user may select that the parts store hold the part for pickup and prepay for the part.

The search returned may be based on various factors. In one embodiment, the results may be based on stores such as part stores (NAPA, AutoZone, Pep Boys, etc.) or Internet stores (Amazon, CARQUEST, etc.) that the technician or garage has an account with. This may assure the technician that he's getting the proper discount and/or preferred delivery method. In another embodiment, the results may be based on the availability of the part, whether the part is an original equipment manufacturer (OEM) part, aftermarket part or generic part.

In still another embodiment, the results may be based on pricing and/or location of the nearest parts store or if the parts store is on the way to or from work for the technician or the vehicle owner. As the tool includes GPS capabilities, the location of the diagnostic tool and by extension, the location of the technician is known, the search engine may be configured to factor in the location of the diagnostic tool. Additionally, the technician or user can preprogram the tool for other locations as a starting location, such as his home, the school or day care of his children, his favorite restaurant and the like. This allows the technician to pick up the part and make sure that the part is correct before he leaves the store. In one embodiment, the technician could take a picture of the faulty part with the camera of the diagnostic tool and bring the diagnostic tool with him for comparison or alternatively email or text the picture to his smartphone for reference. This may be beneficial as the parts database may contain error or parts change but the part number remains the same.

If the technician is satisfied with one of the results, he may select a buy icon 1506. He may select ignore icon 1504 to ignore the result. If none of the icons is selected, the technician may move on to the next result by selecting the scroll icon 1508. In another embodiment, body 1502 may also include a hold or wish list icon (not shown) so that the part may be put on hold until a final decision to purchase is made. This way, the technician is assured that he will have the part to purchase and that it would not be sold out by the time he receives permission to purchase the part by the customer. In the event, that the part is not available due to computer error, that the part was accidently sold, or the desired part is obsolete, the search result may also provide equivalent or similar part.

When pressed, the buy icon 1506 may allow the technician to purchase the part by logging into the parts store's server to purchase the part. The diagnostic tool may be preprogrammed with the user's login information including username and password to make the purchase more efficient. By using a login, the part supplier's server may be able to keep track of the purchases by the technician or service garage for other uses or benefits, such as providing loyalty discount, rebates, free or discounted shipping, percentages off the purchase, free part or tools and the like. In an alternative embodiment, the customer may allow the technician to use the customer's log in information so that the customer knows that he is getting good price as the customer trusts a particular part store. Additionally, the customer can also similar get the benefits such as providing loyalty discount, rebates, free or discounted shipping, percentages off the purchase, free part or tools and the like.

In an embodiment of the disclosure, by having the pricing information and availability information of the part, the technician can provide a service manager with the various repair options including parts and labor costs. This allows the service manager to provide better service to the vehicle owner by letting her know the costs of the part and labor and when the vehicle will be ready based on the availability and delivery time of the desired part. The different costs of the part and labor, such as retail versus dealer cost may both be shown to the customer or only the retail or dealer cost may be shown.

It should also be noted that the software implementations, such as the GUI of the disclosure as described herein can be stored on a tangible, non-transitory storage medium, such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a compact disc or digital video disc; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories. Accordingly, the disclosure is considered to include a tangible storage medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations comprising code segments are stored. Additionally, although a diagnostic tool is described herein, the disclosure may be implemented on any computing device (having a processor and a memory) such as a personal computer, notebook, smart phone, a tablet and the like.

The many features and advantages of the disclosure are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the disclosure, which fall within the true spirit, and scope of the disclosure. Further, since numerous modifications and variations will readily occur to those skilled in the art, it is not desired to limit the disclosure to the exact construction and operation illustrated and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope of the disclosure. 

What is claimed is:
 1. A diagnostic tool with a part ordering system, comprising: a processor configured to execute computing instructions; a connector interface configured to connect with a connector in a vehicle and retrieve vehicle diagnostic data from the vehicle; a display in communication with the processor configured to display diagnostic information and part solution information; a wireless communication interface in communication with the processor and configured to communicate with a remote device having a database; and a memory in communication with the processor, the memory containing instructions, that when executed by the processor causes the processor to: retrieve vehicle diagnostic data including diagnostic trouble codes (DTCs); generate, on the display, a first plurality of selectable icons corresponding to individual DTCs; indicate on the display, if available, the part solution information for at least one DTC; generate, on the display, a list of top fixes based on the retrieved DTCs; search for the part solution information including availability, price, and a part supplier; and generate a second selectable icon configured to allow a user to purchase the part.
 2. The diagnostic tool of claim 1 further comprising: generate, on the display, the search result of the part solution information.
 3. The diagnostic tool of claim 1, wherein the search for part solution information is based on a global positioning system determined location of the diagnostic tool.
 4. The diagnostic tool of claim 1, wherein the indication of availability of the part solution include indicating by color, flashing, bolding of letters, or a combination thereof.
 5. The diagnostic tool of claim 1, wherein the first plurality of selectable icons include history information about the individual DTC.
 6. The diagnostic tool of claim 5, wherein the history information includes failed since last clear, current code, or history code.
 7. The diagnostic tool of claim 1, wherein the search for part solution information is based on a delivery time of the part or a preferred part supplier.
 8. A non-transitory machine-readable storage medium comprising machine-readable instructions for causing a processor of a diagnostic tool to execute the method of: retrieving, with the diagnostic tool, vehicle diagnostic data including diagnostic trouble codes (DTCs) from a vehicle; generating, on a display of the diagnostic tool, a first plurality of selectable icons corresponding to individual DTCs; indicating on the display, if available, part solution information for at least one DTC; generating, on the display, a list of top fixes based on the retrieved DTCs; searching for part solution information including availability, price, and a part supplier; and generating a second selectable icon configured to allow a user to purchase the part.
 9. The non-transitory machine-readable storage medium of claim 8 further comprising: generating, on the display, a search result of the part solution information.
 10. The non-transitory machine-readable storage medium of claim 8, wherein the search for part solution information is based on a global positioning system determined location of the diagnostic tool.
 11. The non-transitory machine-readable storage medium of claim 8, wherein the indication of availability of the part solution includes indicating by color, flashing, bolding of letters, or a combination thereof.
 12. The non-transitory machine-readable storage medium of claim 8, wherein the first plurality of selectable icons includes history information about the individual DTC.
 13. The non-transitory machine-readable storage medium of claim 8, wherein the search for part solution information is based on a delivery time of the part or a preferred part supplier.
 14. A computer-implemented method for ordering parts for a vehicle, the method comprising: retrieving, with the diagnostic tool, vehicle diagnostic data including diagnostic trouble codes (DTCs) from the vehicle; generating, on a display of the diagnostic tool, a first plurality of selectable icons corresponding to individual DTCs; indicating on the display, if available, part solution information for at least one DTC; generating, on the display, a list of top fixes based on the retrieved DTCs; searching for part solution information including availability, price and a part supplier; and generating a second selectable icon configured to allow a user to purchase the part.
 15. The computer-implemented method of claim 14 further comprising: generating, on the display, a search result of the part solution information.
 16. The computer-implemented method of claim 14, wherein the search for part information solution is based on a global positioning system determined location of the diagnostic tool.
 17. The computer-implemented method of claim 14, wherein the indication of availability of the part solution information includes indicating by color, flashing, bolding of letters, or a combination thereof.
 18. The computer-implemented method of claim 14, wherein the first plurality of selectable icons includes history information about the individual DTC.
 19. The computer-implemented method of claim 14, wherein the search for part information solution is based on a delivery time of the part or a preferred part supplier.
 20. The computer-implemented method of claim 14, wherein the search for part information solution is based on a location other than the diagnostic tool's location. 